Oracle Utilities Customer Care and Billing Configuration To configure the Oracle Utilities Customer Care and Billing portion of the integration, define the settings for all three integration points. GL Integration Point To enable this integration point you must configure the following information in Oracle Utilities Customer Care and Billing. Configure GL Division You must map your GL Division in Oracle Utilities Customer Care and Billing to the GL Business Unit in Oracle JD Edwards EnterpriseOne Financial Management GL Business Unit. To do this you should first find out what GL Business Units you will be using within the GL. Then create GL Divisions in Oracle Utilities Customer Care and Billing to match these exactly. You can then associate these GL Divisions with the appropriate Service Agreement Types in Oracle Utilities Customer Care and Billing. Configure Distribution Codes You must map your distribution codes in Oracle Utilities Customer Care and Billing with the appropriate GL Accounts in the Oracle JD Edwards EnterpriseOne Financial Management GL. First configure the distribution codes and then assign them to various entities within the Oracle Utilities Customer Care and Billing applications. Oracle JD Edwards EnterpriseOne Financial Management GL accounts is structured using the Business Unit, Object Account code and Subsidiary code. These are set up in your existing Oracle JD Edwards EnterpriseOne Financial Management configuration according to your business practices. Oracle Utilities Customer Care and Billing distribution codes must be configured to mirror the segments in Oracle JD Edwards EnterpriseOne Financial Management. The segment positions in Oracle Utilities Customer Care and Billing are dot '.' separated so that the first segment is the Object Account, and the second segment is the Subsidiary as shown in the following table: Oracle JD Edwards EnterpriseOne Financial Management Account Column name Oracle Utilities Customer Care and Billing Distribution (GL_ACCT) segment position OBJ Position1 SUB Position2 * Use a dot (.) as the delimiter to indicate a break between positions. A sample GL Account string is 202000.10000. When interpreted by the standard mapping in the product this GL Account String in the sub ledger equates to the following in the Oracle JD Edwards EnterpriseOne Financial Management GL: • Object Account 202000 • Subsidiary 10000 Note: The GL Division is mapped to Business Unit in Oracle JD Edwards Chart of Accounts. Example: Field Label Value Comments Distribution Code Example: R-ELERES The distribution code to be used for financial transactions of a certain type. Description Example: Electric residential revenue A description of how the distribution code is used GL Account Algorithm GLCNST-DFLT The standard product, or customer modified algorithm you use for determining the GL Account String from the distribution code. GL Account Details 1 of 1 Create at least one set of account details as needed by your chosen algorithm above. Only one will be used based on status and effective date. Effective Date 01-01-1900 The date you wish following GL Account string to become active and used by the system, and therefore, the integration software. Status Active Only active status accounts will be used by the product and therefore, the integration. GL Account 202000.10000. Input the GL Account String as explained above. Note: Only fields relevant to the integration are included in this table. Configure GLASSIGN, and GLS for Oracle Utilities Customer Care and Billing Extract To successfully execute extracts from Oracle Utilities Customer Care and Billing, two processes must be configured with the appropriate batch parameters and set to run on a scheduled basis. These processes can be scheduled using the Oracle Utilities Customer Care and Billing scheduling tool or an enterprise scheduler that meets the open architecture standards used by Oracle Utilities Customer Care and Billing.